This is a quick set of instructions on how to check, stop and restart the siam service for talking to the UW instruments.

1. ssh into fangtooth.shore.mbari.org under the ops account (ask one of the sensors project folks for the password)

   ssh ops@fangtooth.shore.mbari.org
   

2. Change to the correct directory by running:

   gosiam
   

3. Check on the current status by running:

   listPorts loc -stats
   

   You should see something like:

   SIAM version $Name:  $
   0 DEBUG  NodeUtility [main]: getNodeURL(): input=loc
   22 DEBUG  NodeUtility [main]: Get node proxy from rmi://loc/node
   53 DEBUG  SiamSocketFactory [main]: SiamSocketFactory.createSocket() - host=loc, port=1099, server host=loc
   54 DEBUG  SiamSocketFactory [main]: return new Socket(host, port)...
   121 DEBUG  SiamSocketFactory [main]: SiamSocketFactory.createSocket() - host=134.89.13.33, port=48506, server host=loc
   121 DEBUG  SiamSocketFactory [main]: return new Socket(host, port)...
   Node 1611 has 2 ports
   
   Port name    ISI-ID  Service                              Status    S  : E : R 
   ---------    ------  -------                              ------   ----------- 
   /dev/ttyUW00 1608    WETLabs ECO Chlorophyll Fluorometer  SAMPLING 5961 151 459
   /dev/ttyW200 1615    WH Sentinel ADCP 150kHz s/n 6501     SAMPLING 10654 454 454
   

4. If there are problems, or the S:E:R numbers don't change over the course of 30 minutes or so, it is probably hung and will need to be restarted. This can be done by:

   exitNode loc
   

5. If the system is really wedged and that does not do the trick, you will have to search for the process using:

   ps -ef | grep java
   

   and you should see something like:

   ops      10451 10447  0 May06 ?        00:50:47 java -cp /home/ops/siam/classes:/home/ops/siam/jars/javax.jar:/home/ops/siam/jars/log4j-1.2.13.jar:/home/ops/siam/jars/XModem.jar:/home/ops/siam/jars/jddac-common.jar:/home/ops/siam/jars/jddac-probe-j2me.jar:/home/ops/siam/jars/instrument-proxy.jar:/home/ops/siam/jars/apache-activemq-4.1.1.jar:/home/ops/siam/jars/spring.jar:/home/ops/siam/jars/jaxb-xjc.jar:/home/ops/siam/jars/activation.jar:/home/ops/siam/jars/stax-api-1.0.1.jar:/home/ops/siam/jars/jaxb-api.jar:/home/ops/siam/jars/jaxb-impl.jar:/home/ops/siam/jars/jaxb1-impl.jar:/home/ops/siam/jars/ssds-client-pub-bob.jar -Djava.security.policy=/home/ops/siam/properties/policy -Djava.rmi.server.codebase= -Djava.rmi.dgc.leaseValue=30000 -Dsiam_home=/home/ops/siam -Dlog4j.threshold=INFO -Dsiam.exit.script=/etc/siam/postSIAM -Dsiam.node.log=/home/ops/siam/logs/fangtooth.200805060900 -Dsiam.log4j=/home/ops/siam/properties/siam.log4j moos.deployed.PublishingNodeTest -publish
   

   The first number is the process ID (PID) and you can kill it using:

   kill -9 10451
   

   where you would substitute in your PID instead of the 10451 listed here.

6. Now that SIAM is shutdown, you should be able to restart it using:

   nodeTestPub -publish &
   

   The '-publish' option sends data to SSDS and if you add a -sensors flag it will publish to the JMS queues connect to the Enterprise Service Bus (ESB).